fix(deps): update all dependencies #984
Open
+20
−20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.2.0.2->8.2.10.27.0->0.30.01.17.0.bcr.1->1.17.0.bcr.20.2.13->0.2.148.16.1->9.0.36.8->6.922.04->24.040.8.11->0.8.141.7.0->1.15.03.25.5->4.33.01.4.0->1.4.51.10.2->6.0.11.10.2->6.0.15.10.2->6.0.15.10.2->6.0.15.10.2->6.0.1Release Notes
keith/buildifier-prebuilt (buildifier_prebuilt)
v8.2.1Compare Source
What's Changed
--incompatible_no_implicit_file_exportby @lukasoyen in #122New Contributors
Full Changelog: keith/buildifier-prebuilt@8.2.0.2...8.2.1
Bazel Module Snippet
Workspace Snippet
bazel-contrib/rules_jvm (contrib_rules_jvm)
v0.30.0contrib_rules_jvmonly supportsbzlmod-enabled buildsModule Setup
In your
MODULE.bazel:Important Changes
java_exporttargets. Targets will depend on these rather than individual constituentjava_librarytargets to ensure that eachjava_librarytarget is only included in onejava_exportWhat's Changed
java_importfrom@rules_javaby @RomanVlasenko in #345System.exitis called during a test by @shs96c in #349New Contributors
Full Changelog: bazel-contrib/rules_jvm@v0.29.0...v0.30.0
v0.29.0WORKSPACE snippet:
What's Changed
New Contributors
Full Changelog: bazel-contrib/rules_jvm@v0.28.0...v0.29.0
v0.28.0contrib_rules_jvmonly supportsbzlmod-enabled buildsModule setup
In your
MODULE.bazelWhat's Changed
Full Changelog: bazel-contrib/rules_jvm@v0.27.0...v0.28.0
bazelbuild/rules_cc (rules_cc)
v0.2.14Compare Source
Using bzlmod with Bazel 6 or later:
[Bazel 6] Add
common --enable_bzlmodto.bazelrc.Add to your
MODULE.bazelfile:Using WORKSPACE:
Full Changelog: bazelbuild/rules_cc@0.2.13...0.2.14
bazelbuild/rules_java (rules_java)
v9.0.3Compare Source
Changes since 9.0.2
MODULE.bazel setup
WORKSPACE setup
With Bazel 8.0.0 and before 8.3.0, add the following to your file:
In all cases, add the following to your file:
Using the rules
See the source.
v9.0.2Compare Source
Changes since 9.0.1
MODULE.bazel setup
WORKSPACE setup
With Bazel 8.0.0 and before 8.3.0, add the following to your file:
In all cases, add the following to your file:
Using the rules
See the source.
v9.0.1Compare Source
Changes since 9.0.0
b1376ddAdd support for an unstripped bootclasspathMODULE.bazel setup
WORKSPACE setup
With Bazel 8.0.0 and before 8.3.0, add the following to your file:
In all cases, add the following to your file:
Using the rules
See the source.
v9.0.0Compare Source
Changes since 8.16.1
a27004aUpdate JDKs to latest patch releases (#335)76212e6Include the srcjar (if there is one) in the _validation output group so blaze will check whether the srcjar file actually exists.402b184upgrade java_tools to 17.0 and wire up linux aarch64 prebuilts (#334)36264e4Update zulu JDKs to latest patch release (#327) (#328)7ff9193Fix test class determination error message (#326)1ed307bIncrease maxwarns to -1 (#291)3257e83Re-enableReturnValueIgnorederror prone check6a30ab8Run the bootclasspath through ijar (#324)3cbc18eUpdate abseil-cpp to remove override (#322)MODULE.bazel setup
WORKSPACE setup
With Bazel 8.0.0 and before 8.3.0, add the following to your file:
In all cases, add the following to your file:
Using the rules
See the source.
bazelbuild/rules_jvm_external (rules_jvm_external)
v6.9Compare Source
Please note The lock file format was changed in
rules_jvm_external5.1. If you update and repin your dependencies, your lock file will use the new format.Usage
This version of
rules_jvm_externalrequires Bazel 6.5.0, Bazel 7.6.1 or Bazel 8.This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.
Bzlmod
If you are using Bazel 7 or above, in your
MODULE.bazelfile:To add dependencies, later in your
MODULE.bazelfile:Workspace-based builds
In your
WORKSPACEfile, add:Then, later in your
WORKSPACEfile, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazelfile, reference the targets directly:What's Changed
packagein gradle versions files properly by @shs96c in bazel-contrib#1419installtag has duplicate coordinates by @shs96c in bazel-contrib#1422force_versionfor root module artifact to take precedence by @shs96c in bazel-contrib#1423@package_metadatainfo forjvm_importtargets by @Yannic in bazel-contrib#1410RJE_UNSAFE_CACHEis set by @shs96c in bazel-contrib#1448New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.8...6.9
jacoco/jacoco (org.jacoco:jacoco-maven-plugin)
v0.8.14: 0.8.14Compare Source
New Features
Fixed bugs
Fixed handling of exceptions in chains of safe call operators in Kotlin (GitHub #1819).
Non-functional Changes
v0.8.13: 0.8.13Compare Source
New Features
inlinefunctions (GitHub #1670).inlinefunctions withreifiedtype parameter (GitHub #1670, #1700).JvmSyntheticfunctions (GitHub #1700).getEntriesgenerated by the Kotlin compiler for enum classes is filtered out during generation of report (GitHub #1625).JvmOverloadsannotation are filtered out (GitHub #1768).Fixed bugs
Non-functional Changes
IllegalArgumentExceptionoccurs during reading of zip file (GitHub #1833).v0.8.12: 0.8.12Compare Source
New Features
Fixed bugs
Non-functional Changes
protocolbuffers/protobuf (com.google.protobuf:protobuf-java)
v4.31.1Compare Source
v4.31.0Compare Source
v4.30.2Compare Source
v4.30.1Compare Source
v3.25.8Compare Source
v3.25.7Compare Source
v3.25.6Compare Source
google/truth (com.google.truth:truth)
v1.4.5: 1.4.5assertThat(nullMap).isEmpty()to fail with a useful failure message instead of throwingNullPointerException(and similarly for other "bogus" values, such as negative sizes). (da5d6e9)isInstanceOf(Int::class.java)(and Java'sisInstanceOf(int.class)) a valid way to check forInt/Integerinstances. (974ef19)isWithinto pretty-print numbers in its failure messages. (de78553,07318c2)Integerinstead ofjava.lang.Integer). (0ba72d6)ExpectFailureto never generate "value of" lines based on bytecode. This slightly simplifies writing new tests withExpectFailureand prevents future behavior changes in someExpectFailuretests that already exist. However, it may also require changes to other existingExpectFailuretests to remove or change any assertions about the "value of" line. (3caa0e8)minSdkVersionis now 23 (Marshmallow). This follows the minimum of Google's foundational Android libraries, and we expect it to have no practical impact on users. (c85c75c)@NullMarked. This was making all our types non-null in those environments, since we don't yet use@Nullablein the GWT/J2CL artifact. (6392d37)v1.4.4@NullMarkedannotation from individual classes up to the package to avoid a warning under--release 8. (e107aea)matchesto conditionally suggest usingcontainsMatch. (7e9fc7a)v1.4.3: 1.4.3Known Issue for at least some builds targeting Java 8, fixed in 1.4.4: "unknown enum constant ElementType.MODULE": #1320. As far as we know, this is only a warning, so it should cause practical problems only if you use
-Werroror you perform reflection on@NullMarkedunder a Java 8 runtime.ee680cb)Subject.Factorymethods for Java 8 types. We won't remove them, but you can simplify your code by migrating off them: Just replaceassertAbout(foos()).that(foo)withassertThat(foo)(orabout(foos()).that(foo)withthat(foo)). (59e7a50)v1.4.2: 1.4.2This release is the final step of copying all our methods from
Truth8toTruth. If you have not already migrated your usages fromTruth8toTruth, you may see build errors:In most cases, you can migrate your whole project mechanically:
git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'. (You can make that change before upgrading to Truth 1.4.2 or as part of the same commit.)If you instead need to migrate your project incrementally (for example, because it is very large), you may want to upgrade your version of Truth incrementally, too, following our instructions for 1.3.0 and 1.4.0.
For help
Please feel welcome to open an issue to report problems or request help.
Changelog
Truth.assertThat(Stream)andTruth.assertThat(Optional). This can create build errors, which you can fix by replacing all your references toTruth8with references toTruth. (45782bd)v1.4.1: 1.4.1This release deprecates
Truth8.All its methods have become available on the main
Truthclass. In most cases, you can migrate your whole project mechanically:git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'While we do not plan to delete
Truth8, we recommend migrating off it, at least if you static importassertThat: If you do not migrate, such static imports become ambiguous in Truth 1.4.2, breaking your build.Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.